Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

This is good, but I have one issue. The other guides focus on one language, so you don't switch between languages, but before you're using Kotlin, Ruby, Swift, React in here, we get a dropdown. Not only that, we always get code snippets that aren't available for the selected language.

This is good, but I have one issue. The other guides focus on one language, so you don't switch between languages, but before you're using Kotlin, Ruby, Swift, React in here, we get a dropdown. Not only that, we always get code snippets that aren't available for the selected language.

Yes, good point, but isn't it a limitation of the current implementation? Either <Code> shouldn't be used in such cases, or user needs to jump between languages. What a third solution would be?

This is good, but I have one issue. The other guides focus on one language, so you don't switch between languages, but before you're using Kotlin, Ruby, Swift, React in here, we get a dropdown. Not only that, we always get code snippets that aren't available for the selected language.

Yes, good point, but isn't it a limitation of the current implementation? Either <Code> shouldn't be used in such cases, or user needs to jump between languages. What a third solution would be?

I think it might be possible to wrap these in IF statements, but I'm not sure if that will work, worth a try though!

@maratal To avoid me having to go through all setup and configuration to test this, please can you provide a repo link that I can pull please? :) That will allow me to easily QA, preferably with test steps you used (i.e. what emulator etc..) you used for this?

Also, would it make this whole guide a bit simpler/shorted if we made use of the dashboards ability to send notifications to device/clientId/Channel? We could still have basic code segments to show how its done, but there'd be no need for the additional UI/handling (also this page is due for a refurb).

That's a fair point. But I think there is a real trade-off between completeness and brevity here — having the send functionality in the app gives readers something tangible to run themselves rather than deferring to an external interface for the most satisfying part of the exercise. Also, in general we tend to use Ably CLI for interacting with the service anyway. I would prefer to hear from other team members before cutting this. If the consensus is to go leaner, I am happy to make the change. wdyt @sacOO7 @m-hulbert @AndyTWF